Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

0140

reference: 183-tree-1
name: 0140
tree-preservation-order: undefined
183-tpo-1
uprn
address-text
point: POINT (-0.938704 50.865328)
geometry: MULTIPOLYGON (((-0.938619 50.865318,-0.938622 50.865335,-0.938634 50.865350,-0.938653 50.865362,-0.938676 50.865370,-0.938703 50.865373,-0.938729 50.865371,-0.938753 50.865363,-0.938772 50.865352,-0.938785 50.865337,-0.938789 50.865320,-0.938785 50.865303,-0.938774 50.865288,-0.938755 50.865276,-0.938731 50.865268,-0.938705 50.865265,-0.938679 50.865268,-0.938655 50.865275,-0.938636 50.865287,-0.938623 50.865302,-0.938619 50.865318)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL